Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-69435 | APSC-DV-001010 | SV-84057r1_rule | Medium |
Description |
---|
Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the system. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the information system after the event occurred). As such, they also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response. Successful application events are expected to far outnumber errors. Therefore, success events may be implied by default and not specified in the logs if this behavior is documented. |
STIG | Date |
---|---|
Application Security and Development Security Technical Implementation Guide | 2017-01-09 |
Check Text ( C-69853r1_chk ) |
---|
Review system and application documentation to identify application operation and function. Access the application logs and review the logs to determine if the results of application operations are logged. Successful application events are expected to far outnumber errors. Therefore, success events may be implied by default and not specified in the logs if this behavior is documented. The outcome will be a log record that displays the application event/operation that occurred followed by the result of the operation such as "ERROR", "FAILURE", "SUCCESS" or "PASS". Operation outcomes may also be indicated by numeric code where a "1" might indicate success and a "0" may indicate operation failure. If the application does not produce audit records that contain information regarding the results of application operations, this is a finding. |
Fix Text (F-75611r1_fix) |
---|
Configure the application to include the outcome of application functions or events. |